Repository navigation
chore(deps): update helm release traefik to v42 - #57
renovate-appwrite[bot] wants to merge 1 commit into
Conversation
Code review
Both the install and nightly workflows now pin the Traefik Helm release to version 42.4.0. This updates the chart used by the routing scenarios and nightly install. Note Not approving while a bug finding is open: Update the fixture to the v42 service schema Fix with agent prompt### Issue 1
.github/workflows/test-install.yaml:23
**Update the fixture to the v42 service schema**
Chart v42 no longer accepts `service.type`; the value must be set under `service.spec.type`. `hack/fixtures/traefik-values.yaml` still sets `service.type: ClusterIP`, so Helm rejects the values and both routing install jobs fail (as reflected in the ingress and gateway-api checks); the nightly install uses the same fixture and will fail too.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Walkthrough (2)
Still open from earlier reviews (1)
Reviewed Tip Comment |
| env: | ||
| GATEWAY_API_VERSION: v1.6.2 | ||
| TRAEFIK_CHART_VERSION: 41.6.1 | ||
| TRAEFIK_CHART_VERSION: 42.3.1 |
There was a problem hiding this comment.
Update the fixture to the v42 service schema
Chart v42 no longer accepts service.type; the value must be set under service.spec.type. hack/fixtures/traefik-values.yaml still sets service.type: ClusterIP, so Helm rejects the values and both routing install jobs fail (as reflected in the ingress and gateway-api checks); the nightly install uses the same fixture and will fail too.
Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/workflows/test-install.yaml
Line: 23
Comment:
**Update the fixture to the v42 service schema**
Chart v42 no longer accepts `service.type`; the value must be set under `service.spec.type`. `hack/fixtures/traefik-values.yaml` still sets `service.type: ClusterIP`, so Helm rejects the values and both routing install jobs fail (as reflected in the ingress and gateway-api checks); the nightly install uses the same fixture and will fail too.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.🟡 Minor · bug · Reply if this doesn't apply.
8f2c7b2 to
42e371d
Compare
42e371d to
a89234a
Compare

This PR contains the following updates:
41.6.1→42.4.042.4.1Release Notes
traefik/traefik-helm-chart (traefik)
v42.4.0Compare Source
🚀 Features
🐛 Bug fixes
📦 Others
👌 Traefik version support
v42.3.2Compare Source
🚀 Features
📦 Others
👌 Traefik version support
v42.3.1Compare Source
🚀 Features
🐛 Bug fixes
📦 Others
👌 Traefik version support
v42.3.0Compare Source
🚀 Features
📦 Others
👌 Traefik version support
v42.2.0Compare Source
🚀 Features
📦 Others
👌 Traefik version support
v42.1.3Compare Source
🚀 Features
📦 Others
👌 Traefik version support
v42.1.2Compare Source
🚀 Features
📦 Others
👌 Traefik version support
v42.1.1Compare Source
🚀 Features
📦 Others
👌 Traefik version support
v42.1.0Compare Source
🚀 Features
🐛 Bug fixes
📦 Others
👌 Traefik version support
v42.0.0Compare Source
There are 3 breaking changes in this release
Upgrade Notes
create,update,delete) are no longer granted cluster-wide.Rolenow grants them in the release namespace only, where Traefik Hub writes its Secrets (#2028)hub.transparencyLogs.witnessGroup.witnessesnow defaults tonullandthresholdmust be at least1.threshold,timeoutorfailOpenwithout any witness now fails.💥 BREAKING CHANGES
🚀 Features
🐛 Bug fixes
additionalServicesexample #2023 by @jnoordsij📦 Others
👌 Traefik version support
v41.7.1Compare Source
🚀 Features
📦 Others
👌 Traefik version support
v41.7.0Compare Source
🚀 Features
📦 Others
👌 Traefik version support
Configuration
📅 Schedule: (UTC)
* * * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.